-CFLAGS=-g -Icoldsync
+CFLAGS=-g -Icoldsync -belf -I/usr/local/include/
FMTS=magproto.o gpx.o geo.o gpsman.o mapsend.o mapsource.o \
gpsutil.o tiger.o pcx.o csv.o cetus.o gpspilot.o magnav.o \
The file format for GPSPILOT (http://www.gpspilot.com) was provided
by Ron Parker. GPSbabel can currently read gpspilot files, but not
write them.
+
+ MAGNAV
+
+ Magellan NAV Companion for Palm/OS is not really designed for this
+ sort of use, but its file format is supported and with a little bit
+ of patience you can both read and write NAV Companion waypoints.
+ Please read README.magnav for further tips on getting waypoints
+ in and out of NAV Companion. This conversion is based on partially
+ incomplete reverse-engineering of the record format, so it may not
+ work with all versions of NAV Companion. It has been tested with
+ version 2.10.
PSP
--- /dev/null
+Translating NAV Companion waypoints to another format is as easy
+as with any other format. Just find the Companion_Waypoints database
+in your palm backup directory and use it as the input file.
+
+When translating waypoints back to NAV Companion, though, you need
+to jump through some hoops:
+
+First, you must merge any waypoints that already exist in the database
+in your Palm Backup directory with the ones you are adding; failure to
+do so will result in only the new points being available in NAV Companion,
+even if you give the new database a different name (it will overwrite
+the old database, even in your backup directory. That's a feature of
+PalmOS, not of NAV Companion.)
+
+To merge the databases, use a command line like the following:
+
+gpsbabel -i magnav -f Companion_Waypoints.PDB -i geo -f geocaching.loc -o magnav -F merged.pdb
+
+Second, you must use the installer to install your new PDB file. Don't
+make the mistake of copying it over the existing Companion_Waypoints.PDB
+file; the one on the handheld will overwrite it rather than merging with
+it.
+
+Finally, because NAV Companion is not designed to work with desktop
+applications, you must tell NAV Companion that its waypoints database
+has changed out from under it. One way to do this is to go to the
+waypoints screen and attempt to scroll; that will force it to reread
+the database and fix the record pointers that it keeps on the heap.
--- /dev/null
+GCEBB 3597.203N 08713.470W 0000000m Mountain Bike Heaven by susy13 a
+GC1A37 3609.068N 08667.955W 0000000m The Troll by a182pilot & Famil a
+GC1C2B 3599.627N 08662.012W 0000000m Dive Bomber by JoGPS & family a
+GC25A9 3603.848N 08664.862W 0000000m FOSTER by JoGPS & Family a
+GC2723 3611.218N 08674.177W 0000000m Logan Lighthouse by JoGps & Fa a
+GC2B71 3606.408N 08679.052W 0000000m Ganier Cache by Susy1313 a
+GC309F 3608.777N 08680.973W 0000000m Shy's Hill by FireFighterEng33 a
+GC317A 3605.750N 08689.200W 0000000m GittyUp by JoGPS / Warner Park a
+GC317D 3608.280N 08686.728W 0000000m Inlighting by JoGPS / Warner P a
${PNAME} -i holux -f reference/paris.wpo -o holux -F ${TMPDIR}/paris.wpo
diff reference/paris.wpo ${TMPDIR}/paris.wpo
+# Magellan NAV Companion for PalmOS
+# This format is hard to test, because each record and the database itself
+# contains the time of creation, so two otherwise identical files won't
+# compare accurately. In any case, the files are binary so diff wouldn't
+# like them. So, we convert the reference file to gpsutil and the converted
+# file to gpsutil and make sure they're the same, and that they're the same
+# as one converted on a known-working installation. Unfortunately, this does
+# not verify that the appinfo block was written correctly. However, it does
+# successfully test for some endianness errors that might otherwise go
+# unnoticed.
+${PNAME} -i geo -f geocaching.loc -o magnav -F ${TMPDIR}/magnav.pdb
+${PNAME} -i magnav -f ${TMPDIR}/magnav.pdb -o gpsutil -F ${TMPDIR}/magnav.gpu
+${PNAME} -i magnav -f reference/magnav.pdb -o gpsutil -F ${TMPDIR}/magnavt.gpu
+diff ${TMPDIR}/magnavt.gpu ${TMPDIR}/magnav.gpu
+diff reference/magnavr.gpu ${TMPDIR}/magnav.gpu
+